Storing and Accessing Traffic Data Images in a Limited Bandwidth Environment

ABSTRACT

Systems, methods, and apparatuses are provided for storing and accessing traffic data images in a limited bandwidth environment. A traffic map image database is stored in a navigation device, where the database includes a plurality of traffic map images. A traffic condition is determined for a location of the navigation device. A traffic map image is retrieved from the database using a processor, where the traffic map image reflects the traffic condition for the location of the navigation device. The traffic map image is displayed on the navigation device.

REFERENCE TO RELATED APPLICATIONS

This application is a continuation under 37 C.F.R. § 1.53(b) and 35U.S.C. § 120 of U.S. patent application Ser. No. 15/288,133 filed Oct.7, 2016, which is a divisional under 37 C.F.R. § 1.53(b) and 35 U.S.C. §121 of U.S. patent application Ser. No. 14/243,059 filed Apr. 2, 2014(Attorney Docket No. 10171-14005A (NC84472US)), which is herebyincorporated by reference in its entirety.

FIELD

The following disclosure relates to storing and accessing traffic dataimages, or more particularly, systems and methods for storing andaccessing an image from a database of traffic data images in a limitedbandwidth environment.

BACKGROUND

Representation and distribution of real time traffic information may bedata intensive. Mobile navigation devices (e.g., car or personalnavigation devices) may not be connected to or in communication with anetwork for real time traffic updates. In other cases, the mobilenavigation device may be bandwidth constrained. For example, the mobilenavigation device may only be able to receive and/or transmit up to afew kilobytes per second.

Current techniques designed to transmit traffic information to a mobilenavigation device having bandwidth constraints include radio datasystem-traffic message channel (RDS-TMC) based location referencing,Agora-C map based location referencing, or transport protocol expertsgroup (TPEG) methods. For example, a RDS-TMC or HD radio system may usean AM or FM radio signal to send highly compressed bit streams oftraffic data to a car or personal navigation system. Unfortunately,these current standards and techniques involve “coding up” as many ofthe road segments as possible in terms of pre-defined identifications orusing latitude/longitude based representations. Therefore, there is acontinuing effort to provide improved systems and methods for providingtraffic data for a navigation system in a limited bandwidth environment.

SUMMARY

Systems, methods, and apparatuses are provided for storing and accessingtraffic data images in a limited bandwidth environment. In oneembodiment, the method comprises storing a traffic map image database ina navigation device, the database having a plurality of traffic mapimages. The method further comprises determining a traffic condition fora location of the navigation device. The method further comprisesretrieving, using a processor, a traffic map image from the database,wherein the traffic map image reflects the traffic condition for thelocation of the navigation device. The method further comprisesdisplaying the traffic map image on the navigation device.

In another embodiment, the method comprises determining a real-timetraffic condition for a location. The method further comprisescomparing, using a processor, the real-time traffic condition with aserver database comprising a plurality of traffic map images. The methodfurther comprises selecting a traffic map image from the server databaseto represent the real-time traffic condition, the traffic map imagehaving an identification key associated with the traffic map image. Themethod further comprises transmitting the identification key to anavigation device having a navigation device database comprising theplurality of traffic map images, wherein the navigation device iscapable of retrieving the traffic map image from the navigation devicedatabase for display.

Apparatuses are also provided for determining real time trafficconditions. In one embodiment, a navigation device comprises at leastone processor and at least one memory including computer program codefor one or more programs, wherein the at least one memory and thecomputer program code configured to, with the at least one processor,cause the navigation device to at least perform: (1) store a traffic mapimage database in a navigation device, the database having a pluralityof traffic map images; (2) determine a traffic condition for a locationof the navigation device; (3) retrieve a traffic map image from thedatabase, wherein the traffic map image reflects the traffic conditionfor the location of the navigation device; and (4) display the trafficmap image on the navigation device.

In another embodiment, an apparatus comprises at least one processor andat least one memory including computer program code for one or moreprograms, wherein the at least one memory and the computer program codeconfigured to, with the at least one processor, cause the apparatus toat least perform: (1) determine a real-time traffic condition for alocation; (2) compare the real-time traffic condition with a serverdatabase comprising a plurality of traffic map images; (3) select atraffic map image from the server database to represent the real-timetraffic condition, the traffic map image having an identification keyassociated with the traffic map image; and (4) transmit theidentification key to a navigation device having a navigation devicedatabase comprising the plurality of traffic map images, wherein thenavigation device is capable of retrieving the traffic map image fromthe navigation device database for display.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments are described herein with reference to thefollowing drawings.

FIG. 1 illustrates an example flowchart for storing and accessingtraffic data images in a limited bandwidth environment.

FIG. 2 illustrates an example flowchart for determining and transmittinga real-time traffic condition for a location.

FIG. 3 illustrates an example system for a traffic data image managementsystem.

FIG. 4 illustrates an exemplary navigation device of the system of FIG.3.

FIG. 5 illustrates an exemplary server of the system of FIG. 3.

DETAILED DESCRIPTION

The following embodiments include systems, methods, and apparatuses forstoring and accessing traffic data images in a limited bandwidthenvironment. As used herein, a “limited bandwidth environment” may referto a mobile navigation device unable to receive or transmit data over awireless transmission at a rate of at least 200 kilobits/sec (i.e.,third-generation (3G) standards).

In certain embodiments, within the limited bandwidth environment, thenavigation device may be able to receive and transmit “over the air” AMor FM radio transmission signals (i.e., two-way communication). In someembodiments, the navigation device is able to receive AM or FM radiotransmission signals, but is not able to transmit a signal (i.e.,one-way communication). In other embodiments, a navigation device in thelimited bandwidth environment is unable to receive or transmit anywireless communication signal (i.e., no bandwidth communication). Thismay include devices being operated outside of a cellular networkcoverage area or a device being incapable of access to a network forlack of a subscription to the network.

In limited bandwidth situations, it may be difficult to transmit a largedata file or traffic images to a mobile device efficiently. Therefore,alternative systems and methods are necessary to provide trafficinformation in these limited bandwidth settings. In certain embodiments,a traffic map image database having a plurality of traffic map images isstored locally on a mobile navigation device. A traffic condition may bedetermined or calculated for the mobile navigation device, and an imagefrom the database may be retrieved that matches the determined trafficcondition. The image may then be displayed on the mobile navigationdevice. Such a method may allow for providing traffic informationwithout having to wirelessly transmit large data files or images to themobile navigation device.

Database of Traffic Map Images

A database of a plurality of traffic map images may be developed for anypredefined road network, such as a metropolitan area or city (e.g., aselected number of road segments within a city). In some embodiments, adatabase may be developed for multiple road segments in multiplemetropolitan areas or cities.

Traffic map images may be developed using historical data alone orcombined with real time or predictive traffic data. For example, trafficmap images may be developed based on the collection of data at varioustimes of a weekday, weekend, holiday, etc. Additional images may bedeveloped for abnormal traffic conditions due to inclement weather,accidents, or construction. In certain embodiments, traffic data for aspecific road segment may be collected for specified time segments or“epochs” to build a historical database. In some embodiments, trafficdata may be collected at various epochs of a weekday, weekend, holiday,etc. In some examples, the traffic data is collected for every 5 minuteepoch during rush hour and every 10 minute epoch for “off-hour” times.

Traffic data may be collected for the average speed of the observedvehicles within the road segment, the frequency of vehicles, and/or theaverage heading of the vehicles. In certain embodiments, traffic datamay be collected from probe data extracted from devices (e.g., mobilephones) within the traveling vehicles, or from fixed monitoringlocations.

Based on the collection of traffic data, traffic map images may beformed from the calculated average speed, frequency, and/or heading foreach road or lane segment at each determined time period. The images maybe color-coded to depict the state of traffic for each road segment inthe predefined road network. In other embodiments, the images may bemarked in varying forms of dashed lines, etc. to depict the state oftraffic. A machine-learning algorithm may be used to define what coloror dashed line to code the road segment for each epoch. In someembodiments, the color or dashed line may be determined based on acomparison between the average speed for the epoch and the speed limitfor the road segment. The traffic map image data may be coded or storedin ASCII or XML, for example.

In certain embodiments, the road segment in the traffic map image may becolor-coded green to represent traffic moving at a minimum percentage ofthe defined speed limit for the road segment. For example, the roadsegment may be color-coded green when the average speed is at 80% orgreater of the speed limit (i.e., 80+ km/hr where the speed limit is 100km/hr). Yellow color-codes may represent slower traffic conditions,representing traffic moving at a certain percentage of the defined speedlimit (e.g., average speeds of between 40% and 80% of the speed limit).Red color-codes may represent even slower moving traffic in comparisonto the defined speed limit for the road segment (e.g., average speedsless than 40% of the speed limit). Additional color-coding is alsopossible, such as a black color code designation for stand-still traffic(e.g., average speeds <5% of the speed limit), and orange forconstruction areas.

In certain embodiments, the road segment may include an individualcolor-code or dashed line for each lane of traffic (in each direction oftravel). In other embodiments, the road segment may include multiplecolor-codes or different forms of dashed lines representing fastermoving and slower moving zones within the road segment.

In certain embodiments, an algorithm may be used to color-code or markthe road segments and develop a plurality of traffic map images for theurban location or city. Algorithms such as Random Forest, DecisionTrees, Naïve Bayes, Neural networks, etc., may be used in this process.

The algorithm may also be used to determine the number of unique trafficconditions for the road segment from the historical data or realtime/predictive data. For example, while road traffic data may becollected for every 5-10 minute epoch, the particular road segment mayonly have a handful of unique images that are developed over the entireday, week, month, or year. Only the unique traffic map images may beneeded for storage, and duplicate images may be culled. In certainembodiments, time stamps may still be retained and linked to the uniquetraffic map images. For example, in some embodiments, a single trafficmap image may be developed that depicts typical traffic conditions for aroad segment at 8:30 am, 4:30 pm, and 5:15 pm, on Mondays, Tuesdays,Wednesdays, and Thursdays of non-holiday weekdays. Instead of saving 12images of the same or substantially similar image, only one image may begenerated for storage, with data linking the image to the specifichistorical time stamps.

The number of overall traffic map images developed for the urbanlocation or city may be based on a number of different factorsincluding, but not limited to the overall area of the location/city, thearea of each traffic map image within the location/city, the number ofnode levels for the location/city (i.e., the number of sub-levels orzones within each level), the varying level of detail or types of roadsdepicted in the traffic map image, and/or the number of unique trafficimages for each level or sub-level.

To the extent an end-user may be interested in an expanded perspectiveof traffic in the city, this may be accomplished in two or three nodelevels to represent the entire city, and one or two zoomed in,sub-levels or nodes within the city. To the extent more narrowed orzoomed in views of a location are desired, additional sub-levels ornodes may be added.

In addition to the size of the view depicted, an end-user may beinterested in a high-level perspective of interstate or highway trafficin the city or of the local roads in the city, or some level of detailin between. In these embodiments, a database of traffic map images maybe developed for various levels of detail (e.g., 2, 3, 4, or 5+ levelsof detail). In some embodiments, this may be accomplished in two orthree levels of detail to represent the highway traffic in the entirecity, and one or two sub-levels within the city. To the extent moredetailed perspectives of a location's roads, additional sub-levels ofdetail may be added. The additional sub-levels may require depictions ofadditional road segments (e.g., local roads), and additional traffic mapimages. The levels of detail may be combined with the varying nodelevels, wherein a more zoomed in or smaller area of depiction mayinclude more detailed traffic detail of the local roads in addition tothe highway roads.

The total number of unique traffic map images for a city may beinfluenced by, for example, the number of different roads of interest,the types of varying traffic conditions for the city, and the overallsize of the city. In a smaller urban location or city (e.g., Wichita,Kans.), the overall number of traffic map images developed for thedatabase may be between 10-100 images. In a larger urban location (e.g.,New York, N.Y.), the overall number of traffic map images developed forthe database may be over 100,000 images.

In development of the database, each of the traffic images in thedatabase may be assigned a unique identification number oridentification key to assist in retrieving the image (as discussed ingreater detail below). For example, a different identification key willexist for a zoomed out traffic image containing minimal detail such asthe highway traffic in comparison to a zoomed in traffic imagecontaining more detail such as local road traffic for a similargeographic location.

After development of the database of traffic map images andidentification keys for the specific location or city, the database maybe downloaded or stored on a mobile navigation device for future use. Incertain embodiments, the navigation device's available hard drive memorymay determine how many images or how many locations or cities may bestored locally. The device's available memory may also determine thequality of each traffic map image (i.e., a smaller storage device mayrequire a downgrade in image quality to store the entire database). Forexample, a compressed image may be approximately 2 kilobytes (kb), whilean uncompressed image may be more than 100 kb.

In certain embodiments, the database may be randomly or periodicallyupdated based on revisions in traffic patterns for the location or city(based on continuing monitoring of the road segments and revisions tothe historical traffic database).

Determining a Traffic Condition

Determining the traffic condition and specific traffic map image todisplay may be influenced by the type of bandwidth connectivity of thenavigation device. Different procedures may be followed depending onwhether the navigation device has (1) no bandwidth connectivity, (2)limited bandwidth connectivity with one-way communication from atransmitter to the device, or (3) limited bandwidth connectivity withtwo-way communication between the transmitter and the device.

No Bandwidth Connectivity

In situations with no connectivity, traffic conditions may be displayedbased on the unique set of traffic map images stored on the navigationdevice and the identification key associated with those images. Forexample, the database stored on the navigation device may include alookup mechanism to provide the closest image that most resembles thereal time traffic conditions in the general vicinity of the navigationdevice. The lookup system may determine a specific identification keyassociated with a specific traffic map image stored on the device. Incertain embodiments, where the navigation device has no connectivity,the lookup system may determine the specific identification key based ona number of off-line or historical factors, such as (1) geographic fenceor location of the image to be pulled, (2) the road network filter(i.e., the level of detail or types of roads depicted in the traffic mapimage), (3) the zoom level within the geographic fence, and/or (4) thetime stamp(s) associated with the image.

For example, in situations where the navigation device may only be ableto provide information to the lookup system regarding the current timeof the device (i.e., time of day, time of week/month/year), the lookupsystem may be able to retrieve identification key(s) associated withthat particular time. The identification key or keys, as discussedabove, may be linked to traffic map images related to historical trafficconditions for the urban location or city at that particular time ofday/week/month/year.

If no further information is available regarding the specific locationof the navigation device itself, the lookup system may select theidentification key associated with the broadest, most high-level area ofthe city. Such an identification key may be linked to a traffic mapimage depicting the historical traffic conditions of the highways of thecity at the current time of day.

In situations where the geographic location of the navigation device isavailable, the lookup system may use the global position of the deviceto determine whether the navigation device is located on a highway orlocal road. The lookup system may then determine what identification keyto retrieve for the particular time of day (i.e., broad area or zoomedin area; highway detail, local road detail, or some level in between).

In some embodiments, an end-user or operator of the navigation devicemay influence the traffic map image to be pulled based on the user's owninput. For example, the user may be able to provide input to thenavigation device regarding the location of the navigation device, thelevel of detail requested, or the zoom level requested. Based on theuser input, the lookup system may determine the correct identificationkey and traffic map image based on the additional information providedby the user.

Limited Bandwidth Connectivity—One-Way Communication

In situations with limited connectivity and one-way communicationbetween a transmitter and the navigation device, the navigation devicemay be able to receive transmissions from a transmitter. The transmittermay be in communication with a network having access to real-time orcurrent traffic conditions. The transmitter and network may also be incommunication with a processor capable of running predictive algorithmsto determine traffic conditions for inclement weather, trafficaccidents, or construction scenarios. For example, the predictivealgorithm may be able to calculate what the road traffic may look likein the future based on the weather or a recent traffic accident, and beable to determine what traffic map image to generate.

Therefore, in scenarios of limited bandwidth connectivity and one-waycommunication, traffic conditions may be displayed on the navigationdevice in similar methods as the navigation devices with noconnectivity. For example, the navigation device with one-wayconnectivity may determine an identification key (and associated trafficmap image) to retrieve based on the historical database factorsdiscussed above.

Additionally, the identification key may be determined based on accessto real-time/current traffic conditions and predictive algorithms forinclement weather, construction, or traffic accidents. For example, aprocessor may be able to analyze the current traffic conditions for theurban location or city and compare the current traffic conditions withthe plurality of traffic map images in the database. Using an algorithm,the processor may determine the closest traffic map image (or images)that matches the current traffic conditions.

The processor may instruct the transmitter to relay an over-the-airsignal (e.g., an AM or FM radio signal) to a receiver connected to thenavigation device. The signal may include one or more identificationkeys that correspond with one or more traffic map images stored locallyon the navigation device. Thus, in situations of limited bandwidthconnectivity, current traffic conditions may be transmitted to a devicewithout sending large amounts of data over-the-air. Instead, thenavigation device stores the potentially large data images locally, andmay retrieve them upon instructions from a transmission signal.

In situations of one-way connectivity, the navigation device may not beable to relay its current geographic location to the server. Therefore,the communication from the transmitter to the navigation device mayinclude more than one identification key for further processing locallyon the navigation device. For example, the navigation device may be ableto use a global positioning system locally on the device to determinewhether the navigation device is located on a highway or local road. Alookup system on the device may then determine what identification keyto choose from the transmission signal. In situations where thenavigation device is on a local road, the lookup system may choose anidentification key associated with a more detailed, zoomed in trafficmap image. In situations where the navigation device is on a highway,the lookup system may choose an identification key associated with ahigher level, less detailed traffic map image showing broad coverage ofthe highway traffic only.

As mentioned above, in some embodiments, the end-user or operator of thenavigation device may influence the traffic map image to be pulled basedon the user's own input. For example, the user may be able to provideinput to the navigation device regarding the location of the navigationdevice, the level of detail requested, or the zoom level requested.Based on the user input, the lookup system may determine the correctidentification key and traffic map image based on the informationprovided by the user in combination with the information provided fromthe transmitter.

Limited Bandwidth Connectivity—Two-Way Communication

In situations with limited connectivity and two-way communicationbetween a transmitter/receiver and the navigation device, the navigationdevice may be able to receive transmissions from a transmitter and alsosend transmissions to a receiver. The transmitter/receiver may be incommunication with a network having access to real-time trafficconditions. The transmitter/receiver and network may also be incommunication with a processor capable of running predictive algorithmsto determine traffic conditions for inclement weather, trafficaccidents, or construction scenarios.

Therefore, in scenarios of limited bandwidth connectivity and two-waycommunication, traffic conditions may be displayed on the navigationdevice in similar methods as the navigation devices with no connectivityor one-way connectivity, as discussed above.

In addition to receiving transmission signals containing anidentification key for a transmitter/receiver, the navigation device mayalso be able to send signals to the transmitter/receiver. The navigationdevice transmission signals may include information regarding itscurrent geographic position or user input information such as the levelof detail or zoom level requested. In turn, the transmitter/receiver mayrelay the navigation device information for processing. Suchcommunication from the navigation device may assist in determining thespecific transmission signal to return to the navigation device (e.g.,what identification key to send).

As mentioned above, in these limited bandwidth connectivity situations,current traffic conditions may be transmitted to the navigation devicewithout sending large amounts of data over-the-air, instead relying onretrieval of the image from the navigation device itself. In someembodiments, like no connectivity and one-way limited bandwidthconnectivity, the end-user or operator of the navigation device mayinfluence the traffic map image to be pulled based on the user's owninput.

Retrieving and Displaying the Traffic Condition

After the navigation device has determined the appropriateidentification key or received a signal from an external transmitterwith the appropriate identification key, the navigation device may thenlookup or retrieve the traffic map image associated with theidentification key and display the image on the navigation device or adisplay in communication with the navigation device.

Repeating/Refreshing the Traffic Condition Reporting

The process of determining the traffic condition, determination of theappropriate identification key, retrieval, and display may be repeatedat set or variable intervals of time. In situations of no connectivity,the traffic condition may be updated at a set time interval, wherein thedevice retrieves the next available historical data point stored whenthe current time is comparable with the historical time (e.g., when boththe current time and historical time equal 5:05 p.m. on a non-holidayWednesday). In situations of one-way or two-way limited bandwidthcommunication, traffic condition signals may be relayed to thenavigation device continuously, at set times, or at random times onlywhere the traffic condition has changed from the last reporting.

FIG. 1 illustrates an example flowchart for storing and accessingtraffic data images in a limited bandwidth environment. The process ofthe flowchart may be performed by a navigation device and its processorand/or a server and its processor. Alternatively, another device may beconfigured to perform one or more of the following acts. Additional,fewer, or different acts may be included.

At act S101, a database having a plurality of traffic map images islocally stored on a mobile navigation device. The traffic map images mayinclude road segments that are color-coded or marked with dashed linesto represent the type of traffic pattern present on the road segment ineach of the images.

At act S103, a processor is used to determine a traffic condition at thelocation of the navigation device. In some embodiments, the trafficcondition is determined based on a current time, and the processorretrieves the traffic map image from the database associated with thecurrent time. In other embodiments, the traffic condition is determinedusing an external processor in communication with the navigation device,wherein the external processor analyzes a real-time traffic conditionand relays a transmission signal comprising an identification key to thenavigation device.

At act S105, a traffic map image from the database is retrieved. Incertain embodiments, the processor of the navigation device receives atransmission signal from an external processor including anidentification key, and the processor of the navigation device retrievesthe traffic map image from the database associated with theidentification key.

At act S107, following retrieval of the traffic map image, thenavigation device displays the image on the navigation device.

FIG. 2 illustrates an example flowchart for determining and transmittinga real-time traffic condition to a navigation device in a limitedbandwidth environment. The process of the flowchart may be performed bya navigation device and its processor and/or a server and its processor.Alternatively, another device may be configured to perform one or moreof the following acts. Additional, fewer, or different acts may beincluded.

At act S201, a real-time traffic condition for a location is determined.At act S203, a server processor is used to compare the real-time trafficcondition with a plurality of traffic map images stored in a serverdatabase. At act S205, a traffic map image is selected from the databasethat represents the real-time traffic condition. In certain embodiments,the traffic map image is associated with an identification key. At actS207, the identification key is transmitted to the navigation device,wherein the navigation device is capable of retrieving the traffic mapimage from a navigation device database for display. In certainembodiments, the identification key is transmitted via an AM or FM radiosignal to the navigation device.

As discussed above, storing and accessing traffic data images in alimited bandwidth environment may be performed by a navigation deviceand its processor and/or a server and its processor. FIG. 3 illustratesone embodiment of a traffic data image management system 120. The system120 may include a map developer system 121, a navigation device 122, aworkstation 128, and a network 127. Additional, different, or fewercomponents may be provided.

The navigation device 122 may be a personal navigation device (“PND”), aportable navigation device smart phone, a mobile phone, a personaldigital assistant (“PDA”), a tablet computer, a notebook computer,and/or any other known or later developed mobile device or personalcomputer. Non-limiting embodiments of navigation devices may alsoinclude RDS devices, HD radio devices, mobile phone devices, or carnavigation devices such as Garmin or TomTom.

The map developer system 121 includes a server 125 and a server database123. The developer system 121 may include computer systems and networksof a system operator such as HERE, NAVTEQ, or Nokia Corporation. Theserver database 123 is configured to store traffic map images developedfrom historical traffic data or predictive traffic data. The database123 is also configured to store identification keys associated with thetraffic map images.

The developer system 121, the workstation 128, and the navigation device122 are coupled with the network 127. The phrase “coupled with” isdefined to mean directly connected to or indirectly connected throughone or more intermediate components. Such intermediate components mayinclude hardware and/or software-based components. In certainembodiments, the navigation device 122 may be coupled with the networkthrough a radio transmitter/receiver 130, which may transmit “over theair” radio transmission signals (e.g., an AM or FM signal) to thenavigation device 122. In some embodiments, the radiotransmitter/receiver 130 may receive transmission signals from thenavigation device 122.

The workstation 128 may be a general purpose computer includingprogramming specialized for providing input to the server 125. Forexample, the workstation 128 may provide settings for the server 125.The settings may include a value for the predetermined interval that theserver 125 requests the navigation device 122 to relay currentgeographic locations. The workstation 128 may be used to enter dataindicative of GPS accuracy to the database 123. The workstation 128 mayinclude at least a memory, a processor, and a communication interface.

FIG. 4 illustrates an exemplary navigation device 122 of the system ofFIG. 3. The navigation device 122 includes a processor 200, a memory204, an input device 203, a communication interface 205, positioncircuitry 207, and a display 211. Additional, different, or fewercomponents are possible for the mobile device/personal computer 122. Incertain embodiments, the communication interface 205 of the navigationdevice 122 comprises an AM and/or FM radio receiver. The receiver may bea high-definition radio receiver.

The processor 200 may be configured to receive data indicative of thelocation of the navigation device 122 from the position circuitry 207.The positioning circuitry 207, which is an example of a positioningsystem, is configured to determine a geographic position of thenavigation device 122. The positioning system may also include areceiver and correlation chip to obtain a GPS signal. The positioningcircuitry may include an identifier of a model of the positioningcircuitry 207. The processor 200 may access the identifier and query adatabase or a website to retrieve the accuracy of the positioningcircuitry 207 based on the identifier. The positioning circuitry 207 mayinclude a memory or setting indicative of the accuracy of thepositioning circuitry.

FIG. 5 illustrates an exemplary server 125 of the system of FIG. 3. Theserver 125 includes a processor 300, a communication interface 305, anda memory 301. The server 125 may be coupled to a database 123 and aworkstation 128. The workstation 128 may be used as an input device forthe server 125. In addition, the communication interface 305 is an inputdevice for the server 125. In certain embodiments, the communicationinterface 305 may receive data indicative of use inputs made via theworkstation 128 or the navigation device 122.

The navigation device processor 200 and/or the server processor 300 mayinclude a general processor, digital signal processor, an applicationspecific integrated circuit (ASIC), field programmable gate array(FPGA), analog circuit, digital circuit, combinations thereof, or othernow known or later developed processor. The navigation device processor200 and/or the server processor 300 may be a single device orcombinations of devices, such as associated with a network, distributedprocessing, or cloud computing.

The navigation device processor 200 and/or the server processor 300 mayalso be configured to cause an apparatus to at least perform at leastone of traffic map image retrieval methods described above. For example,the navigation device processor 200 may be configured to perform theprocess: (1) store a traffic map image database having a plurality oftraffic map images in a navigation device; (2) determine a trafficcondition for a location of the navigation device; (3) retrieve atraffic map image from the database, wherein the traffic map imagereflects the traffic condition for the location of the navigationdevice; and (4) display the traffic map image on the navigation device.

In another embodiment, the server processor 300 may be configured toperform the process: (1) determine a real-time traffic condition for alocation; (2) compare the real-time traffic condition with a serverdatabase comprising a plurality of traffic map images; (3) select atraffic map image from the server database to represent the real-timetraffic condition, the traffic map image having an identification keyassociated with the traffic map image; and (4) transmit theidentification key to a navigation device having a navigation devicedatabase comprising the plurality of traffic map images, wherein thenavigation device is capable of retrieving the traffic map image fromthe navigation device database for display.

The memory 204 and/or memory 301 may be a volatile memory or anon-volatile memory. The memory 204 and/or memory 301 may include one ormore of a read only memory (ROM), random access memory (RAM), a flashmemory, an electronic erasable program read only memory (EEPROM), orother type of memory. The memory 204 and/or memory 301 may be removablefrom the navigation device 122, such as a secure digital (SD) memorycard.

The communication interface 205 and/or communication interface 305 mayinclude any operable connection. An operable connection may be one inwhich signals, physical communications, and/or logical communicationsmay be sent and/or received. An operable connection may include aphysical interface, an electrical interface, and/or a data interface.The communication interface 205 and/or communication interface 305provides for wireless and/or wired communications in any now known orlater developed format.

In certain embodiments, determination and retrieval of a traffic mapimage on the navigation device may be used to provide functions for anautonomous vehicle. An autonomous vehicle is self-driving and may bereferred to as a robot vehicle or an automated vehicle. The autonomousvehicle may include passengers but no driver is necessary. Thenavigation device 122 or another computer system in communication withthe navigation device 122 may include instructions for routing thevehicle or operating the vehicle. An estimated travel time may becalculated based on the traffic map data and a route may be chosen basedon the estimate travel time. The computing system may generate drivingcommands for steering the vehicle, shifting gears, increasing anddecreasing the throttle, and braking. The computing system may generateauxiliary commands for controlling the headlights, turn signals,windshield wipers, defrost, or other auxiliary functions not directlyrelated to the movement of the vehicle.

The autonomous vehicle may include sensors for identifying thesurrounding and location of the car. The sensors may include GPS, lightdetection and ranging (LIDAR), radar, and cameras for computer vision.Proximity sensors may aid in parking the vehicle. The proximity sensorsmay detect the curb or adjacent vehicles. The autonomous vehicle mayoptically track and follow lane markings or guide markings on the road.

In the above described embodiments, the network 127 may include wirednetworks, wireless networks, or combinations thereof. The wirelessnetwork may be a cellular telephone network, an 802.11, 802.16, 802.20,or WiMax network. Further, the network 127 may be a public network, suchas the Internet, a private network, such as an intranet, or combinationsthereof, and may utilize a variety of networking protocols now availableor later developed including, but not limited to TCP/IP based networkingprotocols. In certain embodiments, the network may be in communicationwith a radio transmitter/receiver 130 that produces and/or receives AMor FM signal to communicate with the navigation device 122.

While the non-transitory computer-readable medium is described to be asingle medium, the term “computer-readable medium” includes a singlemedium or multiple media, such as a centralized or distributed database,and/or associated caches and servers that store one or more sets ofinstructions. The term “computer-readable medium” shall also include anymedium that is capable of storing, encoding or carrying a set ofinstructions for execution by a processor or that cause a computersystem to perform any one or more of the methods or operations disclosedherein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to capturecarrier wave signals such as a signal communicated over a transmissionmedium. A digital file attachment to an e-mail or other self-containedinformation archive or set of archives may be considered a distributionmedium that is a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

In an alternative embodiment, dedicated hardware implementations, suchas application specific integrated circuits, programmable logic arraysand other hardware devices, can be constructed to implement one or moreof the methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations.

In accordance with various embodiments of the present disclosure, themethods described herein may be implemented by software programsexecutable by a computer system. Further, in an exemplary, non-limitedembodiment, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionality as describedherein.

Although the present specification describes components and functionsthat may be implemented in particular embodiments with reference toparticular standards and protocols, the invention is not limited to suchstandards and protocols. For example, standards for Internet and otherpacket switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP,HTTPS) represent examples of the state of the art. Such standards areperiodically superseded by faster or more efficient equivalents havingessentially the same functions. Accordingly, replacement standards andprotocols having the same or similar functions as those disclosed hereinare considered equivalents thereof.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, and it can bedeployed in any form, including as a standalone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program can be stored in a portion of a filethat holds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

As used in this application, the term “circuitry” or “circuit” refers toall of the following: (a)hardware-only circuit implementations (such asimplementations in only analog and/or digital circuitry) and (b) tocombinations of circuits and software (and/or firmware), such as (asapplicable): (i) to a combination of processor(s) or (ii) to portions ofprocessor(s)/software (including digital signal processor(s)), software,and memory(ies) that work together to cause an apparatus, such as amobile phone or server, to perform various functions) and (c) tocircuits, such as a microprocessor(s) or a portion of amicroprocessor(s), that require software or firmware for operation, evenif the software or firmware is not physically present.

This definition of “circuitry” applies to all uses of this term in thisapplication, including in any claims. As a further example, as used inthis application, the term “circuitry” would also cover animplementation of merely a processor (or multiple processors) or portionof a processor and its (or their) accompanying software and/or firmware.The term “circuitry” would also cover, for example and if applicable tothe particular claim element, a baseband integrated circuit orapplications processor integrated circuit for a mobile phone or asimilar integrated circuit in server, a cellular network device, orother network device.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andanyone or more processors of any kind of digital computer. Generally, aprocessor receives instructions and data from a read only memory or arandom access memory or both. The essential elements of a computer are aprocessor for performing instructions and one or more memory devices forstoring instructions and data. Generally, a computer also includes, orbe operatively coupled to receive data from or transfer data to, orboth, one or more mass storage devices for storing data, e.g., magnetic,magneto optical disks, or optical disks. However, a computer need nothave such devices. Moreover, a computer can be embedded in anotherdevice, e.g., a mobile telephone, a personal digital assistant (PDA), amobile audio player, a Global Positioning System (GPS) receiver, to namejust a few. Computer readable media suitable for storing computerprogram instructions and data include all forms of non-volatile memory,media and memory devices, including by way of example semiconductormemory devices, e.g., E PROM, EEPROM, and flash memory devices; magneticdisks, e.g., internal hard disks or removable disks; magneto opticaldisks; and CD ROM and DVD-ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a devicehaving a display, e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor, for displaying information to the user and a keyboardand a pointing device, e.g., a mouse or a trackball, by which the usercan provide input to the computer. Other kinds of devices can be used toprovide for interaction with a user as well; for example, feedbackprovided to the user can be any form of sensory feedback, e.g., visualfeedback, auditory feedback, or tactile feedback; and input from theuser can be received in any form, including acoustic, speech, or tactileinput.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back end, middleware, or front end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The illustrations of the embodiments described herein are intended toprovide a general understanding of the structure of the variousembodiments. The illustrations are not intended to serve as a completedescription of all of the elements and features of apparatus and systemsthat utilize the structures or methods described herein. Many otherembodiments may be apparent to those of skill in the art upon reviewingthe disclosure. Other embodiments may be utilized and derived from thedisclosure, such that structural and logical substitutions and changesmay be made without departing from the scope of the disclosure.Additionally, the illustrations are merely representational and may notbe drawn to scale. Certain proportions within the illustrations may beexaggerated, while other proportions may be minimized. Accordingly, thedisclosure and the figures are to be regarded as illustrative ratherthan restrictive.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the invention or of what may beclaimed, but rather as descriptions of features specific to particularembodiments of the invention. Certain features that are described inthis specification in the context of separate embodiments can also beimplemented in combination in a single embodiment. Conversely, variousfeatures that are described in the context of a single embodiment canalso be implemented in multiple embodiments separately or in anysuitable sub-combination. Moreover, although features may be describedabove as acting in certain combinations and even initially claimed assuch, one or more features from a claimed combination can in some casesbe excised from the combination, and the claimed combination may bedirected to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings and describedherein in a particular order, this should not be understood as requiringthat such operations be performed in the particular order shown or insequential order, or that all illustrated operations be performed, toachieve desirable results. In certain circumstances, multitasking andparallel processing may be advantageous. Moreover, the separation ofvarious system components in the embodiments described above should notbe understood as requiring such separation in all embodiments, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

One or more embodiments of the disclosure may be referred to herein,individually and/or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any particular invention or inventive concept. Moreover,although specific embodiments have been illustrated and describedherein, it should be appreciated that any subsequent arrangementdesigned to achieve the same or similar purpose may be substituted forthe specific embodiments shown. This disclosure is intended to cover anyand all subsequent adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, are apparent to those of skill in the artupon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be usedto interpret or limit the scope or meaning of the claims. In addition,in the foregoing Detailed Description, various features may be groupedtogether or described in a single embodiment for the purpose ofstreamlining the disclosure. This disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may be directed toless than all of the features of any of the disclosed embodiments. Thus,the following claims are incorporated into the Detailed Description,with each claim standing on its own as defining separately claimedsubject matter.

It is intended that the foregoing detailed description be regarded asillustrative rather than limiting and that it is understood that thefollowing claims including all equivalents are intended to define thescope of the invention. The claims should not be read as limited to thedescribed order or elements unless stated to that effect. Therefore, allembodiments that come within the scope and spirit of the followingclaims and equivalents thereto are claimed as the invention.

What is claimed is:
 1. A method comprising: storing a plurality of mapimages in a database of a mobile device; detecting a location of themobile device; identifying a real time condition for the location of themobile device; and selecting a map image from the plurality of mapimages representative of the real time condition.
 2. The method of claim1, wherein the plurality of map images are stored before the real timecondition occurs.
 3. The method of claim 1, wherein the selected mapimage includes roads coded according to the real time condition.
 4. Themethod of claim 1, wherein the selected map image includes trafficcodes.
 5. The method of claim 1, wherein each of the plurality of mapimages corresponds to a different traffic pattern.
 6. The method ofclaim 1, further comprising: sending the location of the mobile deviceto a server; and receiving an identification key from the server,wherein the map image is selected.
 7. The method of claim 6, wherein thereal time condition is identified in response to the identification key.8. The method of claim 6, wherein a data size of the identification keyis smaller than a data size of the selected map image.
 9. The method ofclaim 1, wherein the plurality of map images in the database includeimages at multiple levels of road detail and multiple node levels. 10.The method of claim 9, further comprising: identify a road type for thelocation of the mobile device; and select one of the multiple levels ofroad detail based on the road type for the location of the mobiledevice.
 11. The method of claim 1, further comprising: updating theselected map image according to a time interval.
 12. An apparatuscomprising: a database configured to store a plurality of map images ina database of a mobile device; a positioning device configured todetermine a location of the mobile device; and a controller configuredto identify a location of the mobile device and select a map image fromthe plurality of map images representative of a real time condition forthe location.
 13. The apparatus of claim 12, wherein the plurality ofmap images are stored before the real time condition occurs.
 14. Theapparatus of claim 12, wherein the selected map image includes roadscoded according to the real time condition.
 15. The apparatus of claim12, wherein the selected map image includes traffic codes.
 16. Theapparatus of claim 12, wherein each of the plurality of map imagescorresponds to a different traffic pattern.
 17. The apparatus of claim12, further comprising: a communication interface configured to send thelocation of the mobile device to a server and receive an identificationkey from the server.
 18. The apparatus of claim 17, wherein the realtime condition is identified in response to the identification key. 19.The apparatus of claim 12, wherein the plurality of map images in thedatabase include images at multiple levels of road detail and multiplenode levels.
 20. A non-transitory computer readable medium includinginstructions that when executed are configured to cause a processor toperform: storing a plurality of map images in a database of a mobiledevice; detecting a location of the mobile device; identifying acondition for the location of the mobile device; and selecting a mapimage from the plurality of map images representative of the condition.